Winzipper

home *** CD-ROM | disk | FTP | other *** search

/ Winzipper / Winzipper_ISO.iso / utilities / right fax / README.Z / README.TXT < prev

Wrap

Text File | 1995-10-10 | 27.5 KB | 541 lines

============================================================================ ============================================================================ RightFAX NT v4.02 README (11- Sep-95) ============================================================================ This version has some major additions: 1) New Print Driver Technology Previously, RightFAX had NO PM print driver, NO NT print driver nor any Win95 print driver. Now all 3 have print drivers! All three require running a setup routine, located in the respective \RIGHTFAX\CLIENT directories located beneath the RightFAX structure. These installs will make changes to your local configuration to allow the print drivers to work correctly. 2) Now in a Microsoft Network environments, Lan Manager, Lan Server and NTAS, NO QUEUE, SERVER or print queue TYPE need to be defined, e.g. you can have RightFAX service an unlimited number of servers and print queues. All the queues you want RightFAX to service, need to PRINT TO: \\.\pipe\rightfax. For remote servers, this will also work via, CONNECT TO PRINTER, or by having the queue PRINT TO: \\server\pipe\rightfax. ============================================================================ Other Bug Fixes Included 6 Jun 95 - BD_CTL.C, RESXMIT2.C - Fixes a problem with DTMF settings. It seems that the RightFAX BoardServer Applet was not writing the correct information to the Registry. 6 Jun 95 - BD_CTL.CPL - Fixes a problem in the RightFAX BoardServer Applet where it would not write the correct information to the Registry. 8 Jun 95 - PORTHAND.EXE - Fixed a problem in the RightFAX Queue Handler where printing on the FaxServer would cause the ERROR: "All Threads BUSY". This was due to the Print Manager being to slow, so we corrected the routine to accomodate the Print Manager's speed. 21 Jun 95 - LASERNT.DLL - Fixed a problem where the Service would continually "eat" virtual memory, everytime the CONVERTOR DLL was loaded. This would continue until all the memory was eaten. The problem was caused because by Microsoft does not clean up memeory after a DLL is unloaded. The memory it used never would be released and thus the problem. 11 Jul 95 - BROOKSRV.EXE - Fixed a problem in the where it would stop processing for no reason, usually only on 8 fax channels or more. 11 Jul 95 - WORKSRV.EXE - Fixed a problem with OCR incoming faxes for routing. 12 Jul 95 - BD_CTL.CPL - Fixed a problem where Call Grouping would disable or enable ONLY, the Max Pages setting in the Channel Setup. 12 Jul 95 - FAXSERV.EXE - Fixed a problem where starting the Service automatically caused it to give and error "Faxserv hung while starting" in the System EventLog. 13 Jul 95 - WORKSERV.EXE - Fixed a problem where the Service would not read the LOGLEVEL correctly. 13 Jul 95 - WORKSERV.EXE - Fixed a problem where the CVL file did not end in a period and would trap the Service. 13 Jul 95 - FAXPRINT.DLL - Fixed a problem where printing a FAX multiple times would cause the the output handle to become invalid. 13 Jul 95 - FAXDB.EXE - Added PIPECMD_SERVERCHECK so OMF could decipher which server his driver was writing information to. 19 Jul 95 - FAXDB.EXE - Fixed a bug in the DELETION routine, forgot to end TRANSACTION. 20 Jul 95 - FAXSERV.EXE, FAXDB.EXE, BROOKSRV.EXE, WORKSRV.EXE, GATEWAY.EXE, PORTHAND.EXE - Changed the LOGGING information in the Event Viewer so it would not give an EventID of 0, which could constantly notify Administrators on NT. Order is as follows: 0xCF00, 0xCF10, 0xCF20, 0xCF3#, 0xCF4#, 0xCF50 21 Jul 95 - GATEWAY.EXE - Changed the launch command to CreateProcess so we can better keep track of memory leaks. 24 Jul 95 - WORKSERV.EXE - Fixed a problem where the DAMN cfstrtok. 25 Jul 95 - BD_CTL.CPL - Fixed a problem where the AUDIT_PATH and AUDIT_INIT_STR were not being recorded. 27 Jul 95 - FAXDB.EXE - Fixed a problem where CFSTRTOK was screwing up the FORWARD capability. Removed CFSTRTOK from all listings. 02 Aug 95 - *.C - Changed all the EXEs and DLLs, so that they did not need MSVCRT20.DLL. 03 Aug 95 - G3TOPCX.DLL - Fixed a problem with DCX to G3 conversion. Where the G3 would be the right number of pages, but each page would be ALL the DCX pages. 11 Aug 95 - BROOKSRV.EXE - Fixed a problem with WINK settings in the BTCALL.CFG 17 Aug 95 - WORKSRV.EXE - Removed the SYNCFOD services from the WorkServer Module. Also changed the default services: ARCHIVE was removed. 17 Aug 95 - FAXSERV.EXE - Now when a Network Broadcast is needed, the Fax Server Module creates a file for the RightFAX Message Sender to use 17 Aug 95 - FAXS_CTL.CPL - Fixed a problem in which the TEMP variable was being set as TMP, are processes did not like this. 17 Aug 95 - GATEWAY.EXE, WORKSRV.EXE - Changed these Services to check for TMP or TEMP in the \SOFTWARE\RIGHTFAX area of the registry. 18 Aug 95 - FAXPRINT.DLL - Fixed a problem with the checking for an error, i.e. (w == 255) should have been (w == 0xFFFF), this caused a trap in the DLL. 18 Aug 95 - GATEWAY.EXE - Fixed a problem with multiple receipents from mail, the last person would get 2 faxes. 18 Aug 95 - BD_CTL.CPL - Fixed a problem with the AuditLevel being incorrectly written to the Registry. 18 Aug 95 - GATEWAY.EXE - Changed the process to dynamically attach a drive to a UNC name. 22 Aug 95 - FAXDB.EXE, FAXSERV.EXE, WORKSRV.EXE, GATEWAY.EXE - Changed the connecting of the Services to the Registry. It now closes the Key each time when it is done. 22 Aug 95 - GATE_CTL.CPL - Changed the dialog for better viewing of the information. 25 Aug 95 - GATEWAY.EXE - Changed the way it attachs to a network drive. 25 Aug 95 - WORKSRV.EXE, FAXDB.EXE - Added the memory segment information so that FaxStat could access it. 25 Aug 95 - FAXSTAT.EXE - Added RightFAX Database Information. 29 Aug 95 - FAXSERV.EXE, FAXDB.EXE - Changed the reading of the Registry, to close the key after every opening, I thought I had done it before, guess NOT. This would cause an ERROR:8, in the EventLog, under the RightFAX Server Module. 29 Aug 95 - FAXSTAT.EXE - Added RightFAX WorkServer Information. 29 Aug 95 - FAXS_CTL.CPL - Fixed a problem with the RightFAX Database Module not writing information to the Registry. 31 Aug 95 - FAXSERV.EXE - Fixed a problem with Notification turned off, the Server would hang in reposting events in the queue. 12 Sep 95 - FAXSERV.EXE - Added error checking in the delete llop to match FD_FAX.C. 12 Sep 95 - FAXDB.EXE - Added validity checking for the FAX_SET. Added validity checking for the FAX_SET. Added test for bad DBA. Also turned off VIEWED and PRINTED for the fax record. Forced the Object ID to upper case. Added check for simulated end of set. Removed the code to copy the username, based on the different routing types. 12 Sep 95 - FAXSERV.EXE - Added AUTOPRINTing for all received faxes. Added NEWLIB functionality to the server. Added AUTOPRINTing for all received faxes parameter. Added check for NEWLIB code. 12 Sep 95 - GATEWAY.EXE - Added selectable priority for VIM messages. Added PREVIEW embedded code. 12 Sep 95 - WORKSERV.EXE - Added extras tags to Single Page TIFFs. Added -4 option to tell G3toTIFF to not check for sequential base names, e.g. 123P001.TIF, 123P002.TIF. Also, added closing of file and cleaning up attachments after an error. Added owner_id to the error outputs. Also, added test for CS and transmission history, but no fax body. 12 Sep 95 - G3TOTIFF.DLL - Added -4 parameter option to do sequential base names. 12 Sep 95 - BROOKSRV.EXE - Removed: BfvLineReset(pChnInfo->lp, pChnInfo->szConfigFile); We believe it is trapping the Boardserver on TR-112s. 14 Sep 95 - GATE_CTL.CPL - Removed the "changing" of mail types in the dialog, it now reads from the Registry information entered by the install. 14 Sep 95 - GATEWAY.EXE, WORKSRV.EXE - Fixed a problem with using the WorkServer remotely, had a RegOpenKeyEx on a closed handle. 14 Sep 95 - GATEWAY.EXE - Changed the way the gateway looks for its Registry entries. Now, you can install it into any directory beneath RightFAX and it will look for that entry in the Registry. This will allow for multiple gateways on a server. 20 Sep 95 - WORKSRV.EXE Fixed the sent-fax archiving function. Previously, one of the parameters passed to the g3totiff process was invalid. 02 Oct 95 - FAXDB.EXE - Fixed a problem with Purging of deleted faxes and certain memory configurations, which would cause FAXDB to trap in the OS/2 server. 02 Oct 95 - WORKSRV.EXE, GATEWAY.EXE - Added a function to return the USERID for a given fax, to the FAXSTAT program. 02 Oct 95 - FAXSTAT.EXE - Added the Gateway to the Status program. 03 Oct 95 - FAXS_CTL.CPL, BD_CTL.CPL, WORK_CTL.CPL - Changed the way the Applets accessed the Service Manager Database, to hopefully cure the 'ERROR 8' problem. 03 Oct 95 - FAXSTAT.EXE - Added more information to the Gateway section. 04 Oct 95 - WORKSRV.EXE Added a new embedded code <UNIQUEID> for fax coversheets which displays the unique ID associated with a fax. Unique ID's can be assigned to a fax using the embedded code <UNIQUEID:xxxxx>. If no ID is assigned with the embedded code, one will be created by the server automatically. Note that while the field is named Unique ID, the server does not check that duplicate ID's are not being assigned, thus if the <UNIQUEID:xxxxx> code is employed, guaranteed uniqueness is left up to the creator. 05 Oct 95 - FAXSERV.EXE, FAXDB.EXE, BROOKSRV.EXE, WORKSRV.EXE, GATEWAY.EXE, PORTHAND.EXE - Changed all the Registry calls to use the minimum access required to do the calls. 05 Oct 95 - FAXS_CTL.CPL - Added the ability to check which queues are the RightFAX queues and add the Separator File to them. ============================================================================ Helpful Tips -> When using the Export/Report function from FaxAdmin for Windows, we strongly recommend that you set your TEMP environment variable in the AUTOEXEC.BAT to C:\TMP and create a C:\TMP directory. -> The RightFAX Windows Print Driver supplied in version 3.50 and 3.51 will continue to work with RightFAX 4.02 servers. The Driver will not be updated nor is it included with RightFAX 4.02 -- the PowerBar has replaced the Windows Print Driver. -> In order to Print or Preview reports from FaxAdmin for Windows, the "current directory" must be writable. In other words, you may have to set the Working Directory for the FaxAdmin icon to point to a directory on your "home" or local drive. -> The PowerBar is not compatible with Windows NT workstations. There is software included for Windows 95 in the CLIENT\WIN95 directory. Print drivers for Windows NT are not included, though FUW and FAW work. ============================================================================ Troubleshooting Will the RightFAX NT v4.02 work with a Novell network? -> Yes, RightFAX NT v4.02 will work with Novell clients, if they are running multiple protocols, ie Netware and Microsoft requesters. Why is RightFAX creating "weird" usernames, e.g. "<WHO:TOM>" and "/*======"? -> The separator file, which needs to be set in the Printer Setup, was set incorrectly, or not set at all. This was a omission from the manuals. You need to open the PROPERTIES for the queue and goto to the DETAILS section. Then you need to "browse" the \RIGHTFAX\BIN directory for a SEPARATOR FILE called RIGHTFAX.SEP. Nothing needs to be restarted or rebooted for this change to take place. Whenever printing, archiving, or file routing; RightFAX returns an error? -> The RightFAX WorkServer# Modules need to LOG ON AS a user in the Service section. This was an omission from the manual. All Service which access a UNC name, share or path need to have access, other than just SYSTEM access. By default, Windows NT does not allow SYSTEM accounts access to UNC names, shares or paths. You need to open the Service applet in the Control Panel and highlight the RightFAX WorkServer# Module. Then click the STARTUP button. Inside this dialog, click the THIS ACCOUNT button and type in a Username or select the button with the three dots on it, to choose from users in the Domain. Then type in the Users password and confirm it. This will log the RightFAX WorkServer# Module on as that Username. RightFAX NT doesn't do automatic backups? -> That is correct. In Windows NT there is a built in scheduler, which you can take advantage of and backup up the database files. There is a command called "AT", this is a UNIX throw back. It allows you to set a time adn day when you would like something to happen. i.e. run a batch file. All you need to do is create a batch file to STOP the RightFAX Server Module, zip up the files and then re-start the RightFAX Server Module. Then have the "AT" command execute the batch everyday at 10:00PM. You will need to make sure the Service SCHEDULE is running and is set to automatically start everytime you stop the Server. There is a sample batch file included with RightFAX NT v4.02, in the \RIGHTFAX\BIN directory. You will also need to have the service SCHEDULE, LOG ON AS a User, just like the RightFAX WorkServer# Module; since it needs to access a UNC name. ============================================================================ RightFAX NT v4.02 Notes 1) Lack of E-Mail Support This version of RightFAX will NOT support all the E-Mail gateways supported by RightFAX v4.01 for OS/2. RightFAX NT v4.0 does have a GroupWise and MSMail gateway and expects to have a 32-bit Windows NT Service for cc:Mail and Lotus Notes, later this year as the e-mail vendors provide 32-bit Windows NT DLL's. Also, the Gateway can not do conversion of native documents to PCL-5. This means attachments can not be DOC, WP5, SMI files as in the RightFAX OS/2 Gateways. ============================================================================ ============================================================================ RightFAX WindowNT Client Package This package includes all software necessary to support WindowsNT clients with the RightFAX NT 4.02 fax server. The FaxUtil and FaxAdmin programs are similar to the Windows 3.1 versions. The PowerBar, which is available on Windows 3.1, is not available for WindowsNT as the PowerBar framework does not fit the new interface of WinNT. A similar pop-up interface has been developed for WinNT which allows any Win-16 or Win-32 application to fax using an HP LaserJet III or PostScript driver. By using a standard PCL-5 or PostScript driver, documents are maintained as they would print in the most exacting specifications. TrueType, PCL-5, and Adobe fonts are all supported. Like RightFAX on Windows 3.1, the fax processing is all handled by the fax server and the client workstations are all free to go about their work. ============================================================================ Installation of the RightFAX WindowsNT Print Driver 1) Choose 'Create Printer'.. from the Printer menu in the Print Manager. 2) Then enter a name for the Printer. 3) Next select 'Other..', from the Driver selection: enter the location of the \RIGHTFAX\WINNT directory. 4) For 'Description', enter anything you like. 5) Lastly, for 'Print to:', enter the UNC name of the faxqueue, i.e. \\SERVER1\HPFAX ============================================================================ ============================================================================ RightFAX OS/2 PM Driver - (11- Sep-95) Also, please note that this is a 32-bit driver, and thus, will only work with versions of OS/2 above 2.0. ============================================================================ General Overview of the RightFAX OS/2 PM Driver The RightFAX PM print driver provides the user with a pop-up dialog in which fax destination information may be entered. This service can only be provided for OS/2 Presentation Manager (PM) applications. Character-based OS/2, DOS, and Windows applications will *NOT* benefit from this driver. In order to print from such applications, please see the options below. Windows applications running under OS/2 may also use the RightFAX Windows print driver which is shipped with the RightFAX package. Using this driver allows the user to fax directly from a PM application without having to separately start the RightFAX client utility (FAXUTIL). ============================================================================ Options to using this driver include: * Printing from the application to the RightFAX network print queue using a LaserJet, Postscript, or plain-text compatible print driver, then providing fax destination information using the RightFAX client utility (FAXUTIL) which maybe started once and left 'minimized'. * Printing from the application as above, but providing fax destination information within the actual printed document using RightFAX embedded codes, thereby circumventing the need for the client utility (FAXUTIL). * After this driver is installed, the user may print from PM applications by choosing the newly-installed printer object as the print destination for the application. ============================================================================ Installation of the RightFAX OS/2 PM Driver 1) Drag a printer template from the your OS/2 System's Templates folder in order to create a new printer object. 2) In the printer Name field, enter "RightFAX". 3) Click on the Install New Print Driver button. 4) Click on the Other OS/2 Printer Driver button. 5) In the Directory field, enter the directory to your \RIGHTFAX\CLIENT\PM directory. 6) Click on the Refresh button. 7) Double-click on the TIF File Capture driver in order to install it. 8) You should get a message stating that all the required files were successfully installed. 9) Be sure that the TIF File Capture driver is selected in the Default Printer Driver window. 10) Now choose an output port that is not being used for anything else. COM4 is a good choice. 11) Click on the Create button. 12) You should now have a 'RightFAX' printer object. 13) Some initial INI-file settings must be created. In order to do this, go into your \OS2\DLL\MDRIVER directory and execute the following command: "FAXDLG -I" The program should immediately return to the command prompt. ============================================================================ Notes on the RightFAX OS/2 PM Driver * Unlike the other RightFAX client programs (eg. FAXUTIL and FAXADMIN), the driver does NOT bypass your user login if you do not have a password. ============================================================================ ============================================================================ RightFAX Windows-95 Client Package This package includes all software necessary to support Windows-95 clients with the RightFAX NT 4.02 fax server. The FaxUtil and FaxAdmin programs are similar to the Windows 3.1 versions. The PowerBar, which is available on Windows 3.1, is not available for Windows-95 as the PowerBar framework does not fit the new interface of Win-95. A similar pop-up interface has been developed for Win-95 which allows any Win-16 or Win-32 application to fax using an HP LaserJet III or PostScript driver. By using a standard PCL-5 or PostScript driver, documents are maintained as they would print in the most exacting specifications. TrueType, PCL-5, and Adobe fonts are all supported. Like RightFAX on Windows 3.1, the fax processing is all handled by the fax server and the client workstations are all free to go about their work. ============================================================================ Workstation Requirements RightFAX 4.0 NT * Must have Client for Microsoft Networks installed * Must have NetBEUI, IPX./SPX-compatible Protocol (i.e. Microsoft's IPX, not Novell's IPX), or Microsoft's TCP/IP installed * One or more of the aforementioned protocols must be bound to the Client For Microsoft Networks * Must have a Windows-95 version of an HP LaserJet III driver available (this driver is shipped with Win-95). RightFAX 4.0 on Netware Networks (using Warp or OS/2) * Must have Client for Netware Networks installed (i.e. Microsoft's 32-bit Netware requester) or use the latest VLM's from Novell with the appropriate setup in Win-95. Instructions for setting up Win-95 to work with VLM's are detailed in the Win-95 Resource Kit available from Microsoft. RightFAX has not been tested with NETX under Win-95 and no such testing will occur since Microsoft's Client for Netware Networks does all NETX does only faster. NOTE: in our testing we have found that use of VLM's instead of a 32-bit requester will result in dismal performance and reliability problems for Windows applications doing direct IPX calls (e.g. RightFAX). VLM's will not be supported after Microsoft and/or Novell release their 32-bit NDS compatible requesters for Win-95. * Must have IPX./SPX-compatible Protocol (i.e. Microsoft's IPX installed). Novell's IPX may be installed in addition to Microsoft's, but Microsoft's IPX provides IPX support for Windows applications. Without Microsoft's IPX protocol installed, Windows applications written to Novell's API's will think that IPX is not installed and such applications will not operate. * Must have a Windows-95 version of an HP LaserJet III or Apple LaserWriter II NTX driver available (both of these are shipped with Win-95). ============================================================================ Installation 1) Choose Run... from the TaskBar Start menu and enter: J:\RIGHTFAX\CLIENT\WIN95\setup.exe, or \\SERVER\RIGHTFAX\CLIENT\WIN95\setup.exe 2) The Setup Wizard will install the RightFAX software in the folder of choice and will add a new Control Panel applet to the system. 4) Open the Printers folder (either from Control Panel or from the Settings... menu on the TaskBar). 5) Add a new network printer (do not choose Local Printer): Connect the printer to the RightFAX network fax queue: (You can answer Yes or No to the question, "Do you print from MS-DOS programs?") Next, you will be presented with a list of printer drivers. Choose an HP LaserJet III; or, if you have the optional RightFAX PostScript engine installed, you can alternately pick an Apple LaserWriter II NTX. Do not choose a LaserJet 4, IIID, IIIsi, etc. Finally, you will be presented with a dialog at which you can add a useful description for which to describe the printer: The RightFAX printer should not normally be setup as the default printer. At this point if you elect to print a test page the RightFAX pop-up fax address dialog will not be displayed so the test page printing should be skipped. 6) Go into the Control Panel and double-click the RightFAX Applet. From here you can configure the RightFAX software for target fax server and printers which should prompt for fax addressing: Any printer for which you want the pop-up fax addressing to be enabled must be listed in the Fax Printers list-box. To move a printer, select it in the Available Printers list and click the right arrow button. You must now set the name of the fax server if it is named something other than 'RIGHTFAX.' You can also configure whether to login as a specific RightFAX ID or as the RightFAX ID that matches the network name the user is logged in to the network as. 7) That's it! Happy faxing! ============================================================================ Troubleshooting The RightFAX Fax Addressing dialog never pops up, but the document appears in FaxUtil as 'Info Not Complete'? -> The Spool Settings dialog for the RightFAX printer has the 'Print directly to the printer' option set. The Spool Settings must be set to 'Spool print jobs so program finishes printing faster'. It doesn't really matter if you can have printing start 'after last' or 'after first.' The 'Spool data format ' will always be RAW. -> The print driver to which you are printing is not designated as a RightFAX driver in the RightFAX Control Panel applet. Start the Control Panel, double-click the RightFAX applet, select the desired printer under the Available Printers list and move it to the Fax Printers list with the arrow button. The printer I installed does not show up in the Available Printers list in the RightFAX Control Panel applet? -> Only network printers are shown on the Available Printers list. Local printers are not displayed as they will not work properly. The RightFAX Fax Addressing dialog never pops up and nothing ever appears in FaxUtil? -> The RightFAX printer is not connected to a network print queue, or not connected to the proper network print queue. -> One or more files are missing from the RightFAX directory on the client workstation. -> The appropriate client requester and/or protocols are not installed. Try running the FaxUtil or FaxAdmin programs to verify proper networking software. We are getting various communications errors or errors about not being able to find the fax server? -> Use a 32-bit requester, i.e. the Microsoft Client For Netware Networks, instead of old 16-bit TSR-based DOS stuff, i.e. NETX or VLM's. NETX and VLM's were designed for DOS and Windows 3.1, both of which are 16-bit systems. Win-95 is a 32-bit system -- use 32-bit requesters. Graphics and line drawing is not appearing on fax pages? -> Make sure you are using a LaserJet III driver and not a LaserJet 4 driver. If using a LaserJet 4, graphics must be set to Raster, not HPGL; font downloading must be set to 'bitmap' mode, and printer resolution should be set to 300 DPI, not 600 DP.